-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/public visors advertising #743
Feature/public visors advertising #743
Conversation
…lic-visors-advertising
…lic-visors-advertising
One thing I dislike is that I had to rely on callbacks in autoconnect. This is due to the reason that autoconnect needs transport manager, but importing transport manager introduces dependency cycle: transport package depends on servicedisc package. I'm thinking about restructuring it a better way, maybe splitting some packages. Input on this subject is welcome. |
@i-hate-nicknames I was testing out the PR and |
Weird, I just checked and it generated 1.1.1 for me. Is it possible that you didn't build with |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall good work although some of the implementation details might be improvable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome code, lgtm.
Did you run make format && make check?
Fixes #574
Changes:
On start visor registers itself in the service discovery. Visor attaches IPs of its local active network interface to the request;
If
public_autoconnect
field is set to true in config, visor will try to connect to 5 known visors on its start.